Clarification on CSDM Lifecycle Mapping : LifeCycle Stage & Lifecycle Status

[MDAQUIBK]

Hi All,

We have recently enabled lifecycle mapping in our instance, which has been applied across all relevant tables—including Server, Configuration Item, Hardware, and other classes.

After validating the configuration, we observed several discrepancies in the lifecycle mapping. Specifically, the Install Status, Operational Status, and Hardware Status are not consistently synchronizing with the Lifecycle Stage and Lifecycle Status.

We completed the mapping for each table, but when attempting to update the Install Status and Operational Status to align with the corresponding Lifecycle Stage and Lifecycle Status, the synchronization did not occur. However, when we updated the Hardware Status, the synchronization worked as expected with the lifecycle values.

For example:

• Install Status: Retired

• Operational Status: Non-Operational

• Hardware Status: Installed

• Substatus: In Use

In this scenario, the synchronization resulted in:

• Lifecycle Stage: Operational

• Lifecycle Status: In Use

Ideally, the lifecycle mapping should also respond to changes in Install Status and Operational Status, especially since we defined our mappings based on those fields across different tables. However, it appears that synchronization only takes effect when Hardware Status is updated.

Could you please confirm if this is the expected behavior? If not, are there additional configurations required to enable synchronization based on Install Status and Operational Status? Our organization primarily maintains these two fields and would prefer the lifecycle mapping to align accordingly.

Appreciate your support on this matter 

Thanks ,

Aquib

[RK2]

Hi @MDAQUIBK ,

I have shared the screenshot from the PDI, you can also do the same to compare the data with OOTB mapping.

[A Westervelt · Accepted solution]

This is expected behavior with PI 2.0 enabled per CSDM life-cycle sync Phase 4: Ongoing automated sync operations. Install and Operational status do not synchronize with Life Cycle except at the time of migration with the mappings table. Afterwards, only changes directly to Life Cycle values or the synchronization between Asset/CI legacy statuses will update. This is why you see the sync occurring with the Hardware Status fields.
I'd recommend watching this section of CSDM Lifecycles: Aligning and Transitioning to Xanadu where Scott and Mark talk about the interworkings of status syncs.

[Damhoej]

@A Westervelt I have difficulties to find the exact procedure for enabling PI 2.0, because it is not enabled if I do a life cycle sync.
The manual is not clear on where/how to find PI 2.0