Software Technologies Inventory and Attributes

Description — How far the deployed version has drifted from the versions the supplier currently supports.

Benefit(s) — Converts version data into a conclusion that can be reported and prioritized without consulting a support matrix.

Source — Derived or Manual.

Examples — Current, One Version Behind, Multiple Versions Behind, Unsupported

Notes — Derivable at Run maturity by comparing deployed version against supported versions. Unsupported is the value that should trigger action regardless of how well the technology is running.

Description — A composite judgment of the technology's overall technical condition.

Benefit(s) — Allows portfolio-level comparison and heatmapping across technologies that are otherwise hard to rank against one another.

Source — Calculated.

Notes — Publish the scoring method alongside the score. An unexplained composite invites disagreement about the number rather than action on what it means.

Description — How widely the technology is used across the enterprise.

Benefit(s) — Distinguishes a strategic dependency from a local one, which changes both the risk profile and the cost of removing it.

Source — Derived.

Examples — Enterprise-Wide, Multiple Business Units, Single Team

Notes — Derivable from the count and spread of dependent applications rather than assessed separately.

Description — When the technology was last formally assessed.

Benefit(s) — Establishes whether a health judgment is evidence or an assertion, and surfaces assessments that have gone stale.

Source — Manual.

Notes — A health score older than the assessment cadence should be treated as unknown rather than current.

Description — Narrative findings from the most recent assessment.

Benefit(s) — Carries the qualitative detail a score cannot — the specific concerns, mitigations, and observations that inform later decisions.

Source — Manual.

Notes — Particularly valuable where a technology is technically sound but organizationally fragile, or the reverse.