> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/overview/lifecycle-stages-phases.md). # Lifecycle Stages & Phases The lifecycle stages, phases and lifecycle types YouDesign Command uses to describe an element from its first idea to its retirement. A lifecycle describes the stages and phases an element, such as a business application, passes through during its whole life. Every element moves through five **stages**. Inside each stage, **phases** (also called dispositions) record the specific state, such as Planning, Active or Obsolete. An element can carry several **lifecycle types** side by side, for example an internal lifecycle and the manufacturer's lifecycle. For how to enter dates and read the roadmap in the portal, see [Lifecycle](/command/features/lifecycle.md). ## Lifecycle stages | Stage | What it means | | ------------------ | -------------------------------------------------------------------------------- | | **Initialization** | Preparation and planning, including evaluation, review and approval. | | **Productive** | The element is actively used in the enterprise. | | **Expiration** | The sunset period. The element is being phased out and is not deployed again. | | **Exceptional** | A defined waiver that allows use for a limited period. | | **Non-Productive** | The element is fully removed from productive use. This stage ends the lifecycle. | {% hint style="info" %} **Only start dates are needed** You enter the date each phase starts. A phase ends when the next one starts, so there are no separate end dates to maintain. Any phase in the Non-Productive stage ends the whole lifecycle. {% endhint %} ## Lifecycle phases Each phase describes a period within a stage. A phase change is the result of a decision, or of a natural or forced progression. For example, when a manufacturer stops producing a hardware model, its manufacturer lifecycle moves from General Available to End of Life and then to Obsolete. The number of phases, their order and their colours can be changed by a YouDesign Command administrator. ## Lifecycle types | Lifecycle type | Used for | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Internal** | Elements used inside your organisation. It has two variants: one for **logical objects**, such as business capabilities and information objects, and one for **transformational objects**, such as goals and projects. | | **Usage** | How an element is used, recorded through usage records. | | **Standards** | Whether a pattern, software product or hardware product is an approved standard. It can be applied to any CMDB or CSDM class. | | **Manufacturer** | The lifecycle the manufacturer publishes for a product. Where the data is available, it can be loaded automatically. | {% hint style="info" %} **"Active" rather than "In Production"** For logical objects, YouDesign Command uses the phase name **Active** instead of **In Production**. "In Production" fits deployed instances of things. Most objects managed in YouDesign Command are conceptual or logical. {% endhint %} ![YouDesign Command lifecycle stages and phases](https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-c16529e6fb29d67b3a1ad55d03b236391eb2c5e0%2F2697ab1-UPMX_Lifecycle_Definitions.png?alt=media) ## Default phase colours These are the colours phases have when the application is installed. Your administrator may have changed them. | Colour | Phases | | --------- | ----------------------------------- | | `#BAD5DE` | Concept, Evaluating, Requested | | `#61B7E5` | Planning | | `#2295D3` | Under Review | | `#9CABA5` | Beta | | `#71847C` | Limited Available | | `#00E118` | Rollout | | `#0CAC17` | Active, Standard, General Available | | `#FFB401` | Expiring, End of Life | | `#CB958E` | Waiver, Exception, Extended Support | | `#C00000` | Obsolete | | `#08720F` | Completed | | `#999999` | Canceled, Rejected | | `#1F2232` | Blacklisted | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ins-pi.com/command/overview/lifecycle-stages-phases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.