Are there any definitions or descriptions of the life cycle stages and statuses?

[Simone L_]

Hi all,

Are there definitions or descriptions of each lifecycle stage or status?

I am particularly interested in the following statuses of the logical life cycle process (describes in the CSDM 4.0 whitepaper)

• Pilot (ideation)
• On order (purchase)
• Pre-allocated (purchase)
• Available (inventory)
• Obsolete (end of life)

Kind regards,

Simone

[Mark Bodman]

The current values for Logical and Physical CI's are documented here:

New Lifecycle documentation

The only product feature using them today is the mapping functionality from legacy lifecycles, documented here and managed in the CSDM navigator.

The only product feature that depends on the new lifecycle stage and status fields as of San Diego is the CMDB Data Manager.  Here is documentation that explains how CMDB Data Manager uses the lifecycle data for end-of-life activities at this time.

In time, other products in the platform will migrate to use the new Lifecycle Stage and Status fields. The mapping process described in the second link above will allow old and legacy lifecycles to co-exist for as long as necessary to support the migration efforts across the product teams and customer base.

[Dominic5]

Unfortunately these links now only go to generic "platform capabilities" links that don't seem to have the specific contend referred to above by Mark.

[mkeeney]

What is needed are the actual definitions of the allowed values held inside dropdown lists. Otherwise, practitioners will guess when creating or maintaining records, thereby risking loss of consistency in practices.

[Dominic5]

Agreed.
My client is using the new Life Cycle fields for Business Service, Technical Service and Offering. I'm sure there are other places where these fields are visible ootb now (Vancouver) - I think Service Builder may be one, although I've lost my PDI so can't double check.
However, if considering this approach of not using the legacy Phase/Status fields, be aware that there are currently issues with the Service Builder validation conflicting with the Life Cycle Mapping logic that we're having to work around (following guidance from ServiceNow).
Also that the Life Cycle Mapping is designed to work Legacy-to-LifeCycle, but there are issues trying to run it in reverse.