Applications Inventory and Attributes

The Applications Inventory governs a single class of organizational entity: the application. A record in this inventory represents one discrete software solution — named, owned, purposeful, and costed — that the organization uses to support one or more business capabilities or functions. It is the discrete, nameable software solution that appears on a purchase order, in a license agreement, on an IT asset list, or in a conversation between a business stakeholder and their IT partner. Where the boundary between an application and a system is ambiguous, refer to the Glossary below for governing definitions.

This document is organized into attribute categories, each forming its own subsection. Each subsection contains one part with an attribute table. The table has three columns: Attribute Name, Maturity, and Description and Notes. The Attribute Name column uses bold black text. The Maturity column contains one of three plain-text values — Crawl, Walk, or Run — which the IF4IT website renders with color coding applied by CSS. The Description and Notes column contains labeled sections: Description — (what the attribute captures), Benefit(s) — (the governance value it produces), Source — (whether the attribute is Manually Entered, Derived from another inventory, or Calculated), Examples — (concrete example values, present for format-prescribed and multi-value attributes), and Notes — (implementation guidance, valid values, constraints, or connections to other inventories — omitted when nothing meaningful to add). When a Source is Derived or Calculated, no manual data entry field should be created for that attribute — it is system-populated from the relationship or calculation described.

For the general inventory governance principles that apply to this inventory — including semantic identifier conventions, data quality standards, owner accountability, lifecycle management, AI-assisted population, and the connection to the Enterprise Model — refer to the IF4IT Enterprise Inventory Management Best Practices document.

Every attribute in this document is a recommendation — not a mandate. Enterprises are explicitly encouraged to add attributes specific to their context, rename attributes to match their existing vocabulary, adjust valid value sets to match their organizational standards, collapse or expand attribute categories for their tooling, and sequence Crawl/Walk/Run adoption differently based on their priorities. Three things are discouraged: removing foundational Crawl attributes entirely, since portfolio governance consistently fails without them; ignoring the Source designation for calculated and derived attributes, since manually entering system-populated values creates data quality problems that compound over time; and abandoning the Semantic Identifier convention, since it is the connective tissue that makes cross-inventory traversal and AI-assisted analysis possible in the Enterprise Model.

The Crawl/Walk/Run maturity tagging in this document applies not only to which attributes to collect but also to what tooling is appropriate at each stage. At Crawl maturity, a well-structured shared spreadsheet — Google Sheets, Microsoft Excel shared via SharePoint, or equivalent — is a completely acceptable starting point for this inventory. A spreadsheet with the Crawl-tagged attributes populated for every known application is more valuable than a sophisticated inventory management tool with no data in it. At Walk maturity, a lightweight database, Airtable, Notion, or a basic configuration item structure within an ITSM platform provides the query, filter, and reporting capabilities that spreadsheets make difficult at scale. At Run maturity, a dedicated inventory platform, a ServiceNow APM or ITAM module, or a custom data store integrated with the Enterprise Model supports full API connectivity, automated derivation of calculated attributes, and real-time cross-inventory relationship traversal. Governance discipline and data quality matter far more than tooling sophistication — particularly at Crawl and Walk maturity.

This inventory is a component of the Enterprise Model: every record in it, and every attribute of every record, contributes to the enterprise intelligence platform that connects every IT Management discipline — APM, TPM, Enterprise Architecture, IT Operating Environments, and all others — through the typed relationships of the Enterprise Ontology.