> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/fulfillment/fullfilment-flow/asset-lifecycle-overview.md).

# Asset Lifecycle Overview

#### Asset Lifecycle Overview

The asset lifecycle describes the logical states an asset or service can move through in Equipme over time. Each state represents a distinct phase in the existence of an asset, independent from detailed fulfillment or delivery processes.

This overview helps to understand where an asset currently stands and which lifecycle states can typically follow next. It provides the conceptual foundation for how assets are created, used, changed, returned, or eventually removed.

| Lifecycle State | Description                                                                                      | Typical Next States                             |
| --------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------------------- |
| Defined         | The asset or service exists in the system but has not yet been ordered or activated.             | Ordered, Removed                                |
| Ordered         | The asset has been ordered and is entering the fulfillment process.                              | Provisioning, Removed                           |
| Provisioning    | The asset is being prepared, shipped, manufactured, or otherwise fulfilled.                      | Active, Returned, Removed                       |
| Active          | The asset is in use and assigned to a person, location, or organization.                         | Swap, Successor, Returned, Stored, Unsubscribed |
| Swap            | The asset is being replaced due to defect, loss, or another reason while maintaining continuity. | Active, Returned                                |
| Successor       | A successor asset or service is assigned to replace the current one.                             | Active, Returned                                |
| Returned        | The asset is returned from usage to the provider or warehouse.                                   | Stored, Unsubscribed                            |
| Stored          | The asset exists physically but is not actively assigned or in use.                              | Active, Unsubscribed                            |
| Unsubscribed    | The service or asset lifecycle has ended and is no longer active.                                | None                                            |
| Removed         | The asset or order was cancelled before activation or usage.                                     | Non                                             |

#### Asset Lifecycle Transitions by Action

This table shows how an asset typically moves through its lifecycle based on user or system actions. It complements the lifecycle overview by explaining which actions trigger state changes.

| Current State | Action or Trigger              | Resulting State | Notes                                                |
| ------------- | ------------------------------ | --------------- | ---------------------------------------------------- |
| Defined       | Order is placed                | Ordered         | Asset enters the fulfillment flow.                   |
| Defined       | Order is cancelled             | Removed         | Asset never becomes active.                          |
| Ordered       | Fulfillment starts             | Provisioning    | Covers shipping, manufacturing, or provisioning.     |
| Ordered       | Order is cancelled             | Removed         | Cancellation before activation.                      |
| Provisioning  | Fulfillment completed          | Active          | Asset is assigned and ready for use.                 |
| Provisioning  | Fulfillment cancelled or fails | Removed         | Asset never reaches active usage.                    |
| Active        | Swap initiated                 | Swap            | Replacement due to defect, loss, or similar reasons. |
| Active        | Successor assigned             | Successor       | Planned replacement or upgrade.                      |
| Active        | Return initiated               | Returned        | Asset is sent back after usage.                      |
| Active        | Service is cancelled           | Unsubscribed    | Lifecycle ends after being active.                   |
| Swap          | Replacement completed          | Active          | New asset becomes active.                            |
| Swap          | Asset is returned              | Returned        | Defective or replaced asset is returned.             |
| Successor     | Successor activated            | Active          | New asset replaces the previous one.                 |
| Returned      | Asset stored                   | Stored          | Asset is kept for later reuse.                       |
| Returned      | Asset is removed               | Unsubscribed    | Asset is retired after return.                       |
| Stored        | Asset reassigned               | Active          | Stored asset is put back into use.                   |
| Stored        | Asset retired                  | Unsubscribed    | Stored asset is permanently removed.                 |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.equipme.io/documentation/fulfillment/fullfilment-flow/asset-lifecycle-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.