CMDB Calculation

[NarasimhaRC]

Hi Community,

We have an Application Service that is marked Operational Status = Retired and the related Business Application is Decommissioned. However, Service Availability Results are still being generated.

The active record appears to be in service_offering_commitment, where the Availability commitment is still mapped to either the Configuration Item or Service Offering.

Deleting the Service Offering Commitment stops the calculation, but we do not want to delete the record because we need to preserve historical/audit data.

On the service_offering_commitment form, we have:

- Status Field with choices Active and Decommission

- End Date

- Last Reviewed Date

- Configuration Item

- Service offering

- Service commitment

Our proposed approach is:

1. Set Status Field = Decommission

2. Populate End Date

3. Preserve original CI/Service Offering in custom audit fields

4. If Availability still calculates, clear the active Configuration Item / Service offering mapping after preserving the original values

5. Automate this through Flow Designer when Application Service = Retired or Business Application = Decommissioned

Questions:

1. Does OOTB Availability calculation honor Status Field = Decommission or End Date on service_offering_commitment?

2. Is there an OOTB way to retire/deactivate a Service Offering Commitment without deleting it?

3. Is clearing the CI/Service Offering mapping after preserving values in custom fields acceptable?

4. Can CMDB Data Manager help with this, or does this require custom Flow/Business Rule logic?

Looking for the best-practice CSDM-aligned approach.

Thanks!