Were can I find the "PI 2.0 plugin" + Consequence of not converting to "Life Cycle Stage/status"

[SørenP]

Hi guys

According to the CMDB 5.0 white paper (end page 19 -start page 20), I can read that the plugin(?) "PI2.0" - "will eliminate synchronization efforts between legacy configuration item statuses (intall_status,
operational_status, hardware_status) with Life Cycle Stage and Life Cycle Stage Status."

1.

I can't find this plugin in my PDI or in any customer instance that I know of - and it's is not mentioned in the "CMDB Lifecycle Stage and Stage Status Migration" paper from ServiceNow, here they only mention "Activate the CSDM Activation plugin com.snc.cmdb.csdm.activation" - any hint?

2.

It is not 100% clear to me what the consequence(s) of not converting to "Life Cycle Stage/status" is?

Thanks in advance!

Soeren

[Damhoej]

@Mark Manders If you are not using Life Cycles how do you get the Data Manager to work?
It relies on Life Cycles

[Jim Palmer]

There is technically one consequence of using PI 2.0 and CSDM 5.0 life cycle and that is after implementing, the [operational_status] field needs to be manually synchronised if you're using it for things like filters.

Note: Notwithstanding the principal that CIs inherited from [cmdb_ci_hardware] should be using the [install_status] legacy value (which is synchronised in PI 2.0).

Non hardware CIs like virtual machines, cloud objects, service instances etc. can have differences between the CSDM Life cycle and [operational_status] and this is important when you consider plugins like service mapping which rely on that field.

Which is probably why in the CSDM Data foundations dashboard there's the "CIs with matching Operational Status and Life Cycle Stage" report. That will help you identify data source imports and API imports that may need to have the status fields changed to CSDM life cycles.

See this thread for more on it:

https://www.servicenow.com/community/common-service-data-model-forum/clarification-on-csdm-lifecycle...

[Damhoej]

@Jim Palmer Can you guide me to where I can find PI 2.0? 
I can not figure out how to enable it 😉
In my Zurich PDI there is no sync between legacy install status and install status (as far I can see, but have to test it more)

[Jim Palmer]

@Damhoej 

The Get Well playbook was linked above by Mark Manders.
it's not so much a plugin as an enablement activity. you follow the process and eventually this property gets set to define that you are using PI2.0: 

csdm.lifecycle.sync.between.ci.and.asset.activated

First define mappings from old to new, then perform a once off mapping to align the values, then turn off various syncing functions that were causing issues in pervious releases (managed by the property above).

the best explainer was in the community link i sent above (link courtesy of A. Westervelt) as a youtube by Mark and Scott et al.

youtu.be/AiNy1ADkIzk?si=OWhaa_8rlZVWPi8A&t=1716

the easiest explanation is in these 2 images:
before

after

Note how operational_status has no links and only things with an asset (inherited of cmdb_ci_hardware) has any sync with legacy status fields.

[Damhoej]

@Jim Palmer  Thanx a lot. I must have read it wrong 😞

I was stuck in the loop trying to find the plugin/product to install.
I have understood what happens, but I struggled with the PI 2.0 enabled on the CSDM Dashboard..
This helps a lot