9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans

9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans

Quick Answer: In D365 SCM Asset Management, Asset Lifecycle Models act as state machines that define the permissible sequential transitions an asset can undergo from procurement to disposal. Each stage within a model is an Asset Lifecycle State, which functions as a strict operational stage gate by enabling or disabling capabilities such as creating work orders, scheduling maintenance, or deleting the asset. Functional Location Lifecycle Models provide parallel governance over spatial locations. For temporary equipment transfers to technicians or external project sites, the Asset Loans framework manages check-out reservations, condition assessments, and return processing.

---

Asset Lifecycle Models: The State Machine Architecture

An Asset Lifecycle Model (Asset management > Setup > Assets > Asset lifecycle models) standardizes the operational and governance phases of physical equipment. Rather than allowing users to randomly select any status, the lifecycle model defines the explicit Lifecycle state updates that are reachable from each current state.

Linking Models to Asset Types

Lifecycle models are assigned to Asset Types (Asset management > Setup > Assets > Asset types). All physical assets inheriting that asset type are governed by its lifecycle transitions. For example, a standard production machine lifecycle model might define the following progression:

[Created] ──> [Installed] ──> [Active / Operational] <──> [Under Repair]
                                      │
                                      ├──> [Decommissioned] ──> [Scrapped]
                                      │
                                      └──> [Sold]

If a machine is in the Active state, the lifecycle model can be configured to permit transitions to Under Repair or Decommissioned, while strictly prohibiting a direct jump to Scrapped without passing through decommissioning.

---

Asset Lifecycle States: Stage-Gate Configuration

An Asset Lifecycle State (Asset management > Setup > Assets > Asset lifecycle states) defines the operational posture and system restrictions applied to an asset while in that state.

Stage-Gate Control Parameters

Each lifecycle state provides four critical system toggles that dictate operational behavior:

Lifecycle State Comparison Matrix

[!WARNING] Exam Trap — Hard Deletion Restrictions: In D365 SCM, once an asset has accrued any operational or financial transactions (such as counter updates, maintenance request logs, or posted work order journals), the database referential integrity prevents deletion, even if the lifecycle state has Delete asset checked. The asset must instead transition to Scrapped or Decommissioned.

---

Functional Location Lifecycle Models and States

Just as physical machines transition through operational phases, the physical or logical locations where they reside require parallel lifecycle governance (Asset management > Setup > Functional locations > Functional location lifecycle models and ... > states).

Functional Location Stage Gates

Functional location lifecycle states regulate spatial administration through three critical toggles:

1. Install asset: Controls whether technicians can install physical assets at this functional location. For a location in a Planning or Under Construction state, this toggle is disabled to prevent accidental equipment placement.
2. Create sub-location: Governs whether users can add child functional locations beneath this location in the hierarchy.
3. Create work order: Dictates whether facility-level work orders (such as building repairs, structural painting, or HVAC duct cleaning) can be initiated directly against the functional location.

[Location State: Planning]         --> Install Asset: NO  | Create Work Order: NO
[Location State: Active Service]   --> Install Asset: YES | Create Work Order: YES
[Location State: Renovation]       --> Install Asset: NO  | Create Work Order: YES
[Location State: Decommissioned]   --> Install Asset: NO  | Create Work Order: NO

---

Asset Loans: Tracking Temporary Resource Allocations

In many industrial and field service environments, specialized portable equipment—such as laser alignment kits, thermal imaging cameras, mobile generators, or loaner vehicles—is temporarily assigned to technicians, departments, or external job sites. The Asset Loans framework manages these allocations (Asset management > Asset loans > All asset loans).

1. Registering an Asset Loan

When an asset is requested for checkout, a loan record is authored:

• Loan ID: Unique system sequence identifier.
• Asset: The specific physical asset being checked out.
• Borrower: The worker (linked to Human Resources HCM worker tables) or external entity taking custody.
• Planned loan date/time: Projected checkout window start.
• Expected return date/time: Agreed return milestone.
• Contact information: Phone, site location, or department identifier.

2. Loan Status Lifecycle

The loan record progresses through three sequential stages:

1. Created: Reservation is logged in the system. The asset is scheduled for loan, alerting other planners of impending unavailability.
2. Loaned: The asset is physically handed to the borrower. The asset's availability status is updated, blocking overlapping loan reservations.
3. Returned: The borrower returns the asset to the tool crib or warehouse. Custody is released back to the primary functional location.

3. Return Processing, Inspection, and Utilization Auditing

When an asset is marked as returned (Action Pane > Return asset loan), D365 SCM executes three critical verification steps:

• Actual Return Timestamp: Records the precise date and time of physical return to measure checkout duration and identify overdue loans.
• Condition Assessment: Technicians can complete a condition assessment checklist to document whether the tool sustained physical damage, wear, or missing accessories while on loan.
• Counter Registration: For mobile machinery (such as portable generators or utility trucks), technicians enter the ending odometer or run-hour counter value, capturing the operational usage accumulated during the loan period.
• Maintenance Request Generation: If damage is identified during return inspection, the technician can trigger a corrective maintenance request directly from the loan return screen.

---

Implementation Scenarios and Common Exam Traps

[!TIP] Exam Tip — Restricting Scheduling vs. Restricting Work Order Creation: An exam question may present a scenario where equipment is offline for maintenance and planners must log repair jobs, but the automatic scheduling engine must not dispatch workers until replacement parts arrive. The correct design is to transition the asset to a state where Create work order is selected, but Schedule work order is cleared.

[!IMPORTANT] Exam Tip — Asset Loan Availability Conflicts: D365 SCM validates loan date intervals against existing loans for the same asset. If a planner attempts to register a loan for an asset that is already in Loaned status or has an overlapping Created reservation, the system throws a scheduling validation conflict.

[!WARNING] Exam Trap — Functional Location Decommissioning: Decommissioning a functional location does not automatically scrap the assets installed upon it. The installed assets must be explicitly moved to a new functional location or transitioned to an inactive asset lifecycle state before the location can be retired.