"Before load" logic to ensure data quality in CMDB

[Anish Reghu]

Dear experts,

What is the "before load" logic to ensure data quality in CMDB. I read this in NowCreate. It says:

If you have already implemented it within your organization, consider starting with a stabilized CMDB.

Re-architect existing integrations

1. Leverage IRE for CI matching to ensure alignment with Discovery
2. Replace all delete actions with lifecycle state changes
3. Review consumption of CMDB relationship types
4. Implement "before load" logic to ensure data quality.

Kindly guide.

Regards,

Anish

[Anurag Tripathi · Accepted solution]

It would refer to your transform maps where you do any kind of validation to identify duplicates etc.

[Anish Reghu]

So, in turn it suggests to have all the required "before load" transform scripts in place to avoid duplicate CIs into the CMDB. Did I understand that correct?

[Anurag Tripathi]

That is my understanding. Any logic that needs to run before actual data load to correct and improve data quality

[Pratiksha]

Partially, in most of the cases you may find that the data present at source is not clean. In cmdb we do transforms before sending to target tables. That helps to do the sanity check even before data is been loaded. While loading the data IRE Take care of duplication issue.