Integrations Inventory and Attributes - Lifecycle and Status attributes for the Integrations Inventory

Integrations Inventory and Attributes

Chapter 12. Lifecycle and Status attributes for the Integrations Inventory

Lifecycle and Status attributes track the current governance state of each Integration and the key dates associated with its lifecycle transitions.

Attribute Name	Maturity	Description and Notes
Lifecycle Status	Crawl	Description — The current governance state of this integration record. Benefit(s) — Enables the Integrations Inventory to distinguish live production integrations from planned, under-review, or decommissioned ones. Without Lifecycle Status, a registry of integrations cannot be used for active governance. Source — Manual. Examples — Proposed, Active, Under Review, Deprecated, Retired Notes — Valid values: Proposed, Active, Under Review, Deprecated, Retired. Status changes require inventory owner approval. A Deprecated integration that has not yet been retired should have a Planned Retirement Date populated.
Effective Date	Walk	Description — The date on which this integration became Active in production. Benefit(s) — Supports longitudinal integration portfolio analysis — tracking when integrations were introduced and identifying long-lived integrations that may be modernization candidates. Source — Manual. Examples — 2022-03-01, 2024-07-15
Planned Retirement Date	Walk	Description — The date on which this integration is planned to reach Retired status. Populated only for Deprecated integrations with a defined exit timeline. Benefit(s) — Enables transition planning for integrations scheduled for decommissioning — surfacing which dependent systems and processes must be decoupled before retirement. Source — Manual. Examples — 2026-12-31, 2027-06-30 Notes — Leave empty for Active and Proposed integrations.

Attribute Name

Maturity

Description and Notes

Lifecycle Status

Crawl

Description — The current governance state of this integration record.

Benefit(s) — Enables the Integrations Inventory to distinguish live production integrations from planned, under-review, or decommissioned ones. Without Lifecycle Status, a registry of integrations cannot be used for active governance.

Source — Manual.

Examples — Proposed, Active, Under Review, Deprecated, Retired

Notes — Valid values: Proposed, Active, Under Review, Deprecated, Retired. Status changes require inventory owner approval. A Deprecated integration that has not yet been retired should have a Planned Retirement Date populated.

Effective Date

Walk

Description — The date on which this integration became Active in production.

Benefit(s) — Supports longitudinal integration portfolio analysis — tracking when integrations were introduced and identifying long-lived integrations that may be modernization candidates.

Source — Manual.

Examples — 2022-03-01, 2024-07-15

Planned Retirement Date

Walk

Description — The date on which this integration is planned to reach Retired status. Populated only for Deprecated integrations with a defined exit timeline.

Benefit(s) — Enables transition planning for integrations scheduled for decommissioning — surfacing which dependent systems and processes must be decoupled before retirement.

Source — Manual.

Examples — 2026-12-31, 2027-06-30

Notes — Leave empty for Active and Proposed integrations.

Legal Disclaimers