Maturing Data Impacts to BCM

[jstoessel]

I have a general question as we are working on implementing CSDM. 

Recently we loaded up a bunch of records and put them into the class of Business Application.  After review and more research, we realized that these were the Application Services.

Easy fix, change the class on the records and add additional information.

The problem was that during the 15 days that these records were in the class Business Application, they were used in the Business Continuity Application to generate the start of BIAs (Business Impact Assessments).

The result of the class change was the BIAs no longer could connect to the record class of Business Application, so they were no longer displaying the title of the Business Application.

What is the 'best practice' for managing this data.  I understand that we could/should have created new Application Service records instead of changing the class - but what is the correct way to handle the 'removal' of Business Applications?

What is the lifecycle of an incorrectly entered Business Application?

I also have the same issue with Business Capabilities - since we are on our third 'restart', we have some business capabilities that have three or four records - some dating back to 2019.  How would you combine the important data and handle the lifecycle on this data clean up effort?  They are exact duplicate entries.

Thanks!

[Daniel Borkowi1]

Hi @jstoessel, in your case it's maybe too late, but I strongly recommend not to delete CMDB data which already is in use in tables which are connected to other processes like Business Application- it's analog with moving CIs to other classes (except reclassification by Discovery). Instead using status like install status "deprecated" and instead of moving, clone the data in the new table. 

Greets
Daniel

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Satishkumar B]

Hi @jstoessel 

For handling data issues, particularly with CSDM, best practices include:

1. Business Applications: Instead of changing record classes, it's better to create new records for the correct class. For records that were misclassified, you should ideally archive or mark them as obsolete. Ensure that any related BIAs are updated to reference the correct Application Services.

2. Lifecycle of Incorrect Records: Incorrectly entered records should be either archived or marked as obsolete to maintain historical data integrity while preventing them from being used in active processes.

3. Duplicate Business Capabilities: Combine relevant data from duplicate entries into a single record and archive or delete the duplicates. Maintain a log of changes for historical reference and ensure the cleanup effort is thorough to avoid future duplicates.

This approach ensures data accuracy and integrity while maintaining a clear historical record.

…………………………………………........................................................................................
Mark it helpful 👍and Accept Solution ✅!! If this helps you to understand.

…………………………………………........................................................................................