Buy me a coffee
Eve McGivern

← Tools

Platform guide: Application rationalization

Download Word (.docx)

Where the fields this tool uses live in ServiceNow's Enterprise Architecture and SAM Pro, and in Flexera One. Every module, table, or field named below is confirmed on a source in the Sources list; where no source names one, that is stated as a gap rather than guessed.

ServiceNow Enterprise Architecture (formerly Application Portfolio Management): applications and portfolio assessment

Applications are held as Business Applications (table cmdb_ci_business_app), the object ServiceNow's Enterprise Architecture product treats as the subject of portfolio management. Starting with the Xanadu release, ServiceNow renamed Application Portfolio Management (APM) to Enterprise Architecture, still documented in doc titles and breadcrumbs as "Enterprise Architecture (formerly Application Portfolio Management)"; ServiceNow frames the rename as additive rather than a removal of any APM capability, broadening scope beyond a single application portfolio into wider enterprise modeling. Portfolio assessment runs through Assessment Indicators — individual evaluation criteria such as cost, risk, quality, or usability — grouped into a Scoring Profile, which weights the indicators for a given assessment context and produces an Application Score per app. Assessments cover named dimensions including cost, quality, technical risk, investment, user satisfaction, and business value, matching the business-value and technical-fit split this method scores on. Results surface through an Application 360 view and bubble-chart visualizations, and from Xanadu onward through the Enterprise Architecture Workspace (EAW)'s "Application Migration & Rationalization" lens as well as the classic Business Application form — both read and write the same underlying records.

Enterprise Architecture's own documentation still frames application portfolio rationalization as a decision to invest, sustain, migrate, or retire an application — its own four labels, not this method's Tolerate/Invest/Migrate/Eliminate wording. Map this tool's TIME output onto Enterprise Architecture by treating Tolerate as "sustain" and Eliminate as "retire"; Invest and Migrate carry over directly. That decision is stored in a field named Planned Disposition on the Business Application, confirmed on ServiceNow's Enterprise Architecture Workspace rationalization documentation and a ServiceNow Community thread titled "Definitions of Planned Disposition values?"; ServiceNow's public documentation does not name the underlying table/column identifier for that field.

ServiceNow's own Application Portfolio Management product page (servicenow.com/products/application-portfolio-management.html) and a Business Application form reference page do not return readable content to an automated fetch — 403 and 404 respectively, including a Washington DC-bundle equivalent of the form page, which also 404'd. The terms above come from ServiceNow docs-bundle pages that did load.

ServiceNow SAM Pro: entitlements and license position

License records are held as Software Entitlements (table alm_license) — the purchase records for owned software. SAM Pro's Reconciliation step matches entitlements against actual installations using its licensing rules engine to produce a License Compliance Position, the record this method's license-expiry and over-entitlement check corresponds to. Each entitlement carries a License Metric (the licensing model, such as per-user or per-processor) and can be enriched from a PPN (Publisher Part Number), the vendor SKU that prefills metric, downgrade rights, and end-of-life data. License consumption rules govern which installations draw against a given entitlement.

ServiceNow's community documentation names the relevant date fields only as "Effective/expiry dates" on the entitlement and "End date" on the linked Contract (ast_contract) record, and confirms that SAM Pro's renewal calendar and dashboard notifications key off the contract's end date, not the entitlement's own end date — a separate community thread describes blank renewal dates as a common data-entry mistake that stops SAM Pro from flagging a renewal. No ServiceNow-published source names a more specific column identifier for either field. This method's checked_on/expiry check maps to that contract-driven renewal-tracking behavior, not to a single named entitlement-expiry column.

Flexera One: application inventory and license position

Flexera One's SaaS inventory comes from comprehensive SaaS discovery feeding a multi-source data engine that combines financial systems, expense reports, API connectors, SSO providers, and browser extensions; on-prem and cloud assets are covered by the same hybrid IT discovery used for application inventory generally. Every discovered title is normalized against Technopedia, which Flexera states recognizes and normalizes titles at over 98%. Duplicate detection is a named capability — application redundancy identification, backed by automated application categorization — which is the direct analog of this method's duplicate-finding step.

License position work uses verified usage metering (login-depth usage data, not just login events) to report active, inactive, and never-active users and cost per user, surfacing unused and unassigned licenses for automated reclamation workflows. Dependency mapping flags what would break before an app is decommissioned, which matters for this method's Migrate/Eliminate data-disposition step. Flexera's own rationalization framing groups outcomes as Re-host, Re-platform, Retire, Retain — its "4 R's" — again a different label set from this method's TIME model; map Retain to Tolerate, Retire to Eliminate, and treat Re-host/Re-platform together as Migrate.

No confirmed Flexera One field or table name exists for storing a rationalization decision itself (TIME or 4 R's); its documented capabilities support the inventory and usage evidence the decision is based on, not a decision record. Flexera's documentation site (docs.flexera.com/...) does not return readable content to automated fetches, so nothing above cites it directly.

Sources checked

Pages that do not return readable content to an automated fetch: ServiceNow's own Application Portfolio Management product page (servicenow.com/products/application-portfolio-management.html, 403) and its Business Application form reference (servicenow.com/docs/r/application-portfolio-management/business-application-form.html, 404, also 404 on the Washington DC-bundle equivalent); and Flexera's documentation site (docs.flexera.com/..., 403). Everything above comes from a page that loaded.