Software Technologies Inventory and Attributes

Description — The organization from which the enterprise obtains the technology, referenced by Semantic Identifier.

Benefit(s) — Connects the technology to vendor risk, support terms, and commercial relationship without restating vendor data here.

Source — Manual.

Notes — Leave empty for open source technologies and populate the governing community attribute instead. A typed reference to the vendors inventory, not free text.

Description — The community, foundation, or steward that governs an open source technology.

Benefit(s) — Records the open source equivalent of a vendor, so the field reads as a different support arrangement rather than an absence of one.

Source — Manual.

Notes — Community health — contributor count, release rhythm, foundation backing — is as consequential as vendor viability and far less often assessed.

Description — The level of support the enterprise is entitled to under its arrangement with the supplier.

Benefit(s) — Establishes what recourse actually exists during an incident, which is frequently assumed rather than verified until it is needed.

Source — Manual.

Examples — Premium, Standard, Basic, None

Notes — A value of None on a technology with a high criticality tier is a finding worth surfacing.

Description — Reference to the governing support agreement.

Benefit(s) — Makes response commitments, escalation paths, and renewal dates retrievable when they matter.

Source — Manual.

Notes — Cross-reference the contract record rather than restating its terms here.

Description — The enterprise's judgment of the supplier's ongoing ability to support the technology.

Benefit(s) — Surfaces supply-side risk before it becomes an emergency — an acquisition, a wind-down, or a community that has stopped releasing.

Source — Derived or Manual.

Notes — Derivable at Run maturity from the vendors inventory. For open source, assess the governing community rather than a vendor.