First activation step — Map existing life cycle data to CSDM standards
You can align life-cycle values for each product instance on the asset, CI, and IBI tables. A one-time process moves legacy data for asset and CI across the platform to standard CSDM life-cycle values. Business rules then ensure identical IBI, asset, and CI life cycle data for each product instance.
- To handle alerts appropriately, Event Management and Operational Intelligence need to know whether a CI is in maintenance life-cycle status.
- To report cost data effectively, Cloud Insights needs to know the state of a CI.
- To generate consistent tasks and workflows, Audit and Compliance need to use standard life cycle values.
You must activate life cycle migration to migrate legacy life cycle values to the CSDM standard fields and values.
Life Cycle Mapping table
The base system contains the Life Cycle Mapping [life_cycle_mapping] table, which is pre-populated with widely used legacy life cycle mappings. Each mapping record specifies how to map a legacy life-cycle field’s value, based on its table, to the standard CSDM values.
- Life cycle stage (life_cycle_stage): The broad life cycle phases that a CI moves through, from inception or procurement to retirement and end of life.
- Life cycle status (life_cycle_stage_status): The specific status of a CI within its current life cycle stage.
The table typically contains multiple record entries per class, each entry for a specific legacy life cycle and life-cycle value pair. When there are multiple record entries for a class, the entries are prioritized by importance and likelihood for containing meaningful values for the mapping process.
- A Life cycle stage is one of the broad phases that a CI moves through, from inception or procurement to retirement and end of life.
- Life cycle stage status is the specific status of a CI within its current life cycle stage.
Custom life cycle values
In an upgrade scenario, life cycle migration checks for custom legacy life-cycle values that were added in the system. For each custom value, the system adds a record to the Life Cycle Mapping [life_cycle_mapping] table. Those mapping records, however, are incomplete and inactive.
Before you activate life cycle migration, you must edit and activate those records to supply the desired life cycle control to use for mapping.