Improve Integration Data Quality
Problems with Integration Data Quality
Integration Data Quality can be a challenging issue to solve. ServiceNow is often a highly integrated platform with incoming integrations for Foundation Data & CMDB as well as transactional data, such as Incidents and Tasks.
Creating integrations is time consuming and difficult to test. Furthermore, integrations often produce only a portion of the needed data and sometimes in non compliant formats.
Enforcing strict rules can lead to data not being accepted and created at all. If it is created, the information may not be complete. Therefore, compromises are often made to get at least some data in.
It is easy to blame integrations for bad data quality. Sometimes it is quietly accepted that data coming from Active Directory, HR systems or vendors’ CMDB’s just isn’t that good and there’s really isn’t much one can do about it.
Multiple problems can arise due to bad quality data coming in through integrations. Here are some typical examples:
- People need to fix the same data over and over again in the target system, while the source continues to feed bad data.
- Integrated data causes problems in reporting and workflows, or reports need to be manually tweaked.
- No way to measure the status of data quality of a given integration.
- Integrated data is not connected to the rest of the platform.
- Tracking the quality of integrated data over time is difficult or impossible.
- Setting and measuring targets for data providers is difficult or impossible.
See How to Improve Integration Data Quality
Data Content Manager for Integrations
Data Content Manager can be used to define specific data requirements for each integration. It can then Audit real data against your requirements so that you can track your integrations data quality.
Data Content Manager helps you to:
- Specify data requirements easily and visually for different integrations.
- Define and measure precisely what each data provider should provide to clarify responsibilities.
- Schedule data audits to keep track of data quality over time.
- Identify deviations as they occur, not when they cause problems.
- Connect integrated data to the rest of the platform with additional Blueprints and Auditing.
- Assign targets for Data providers and enforce meeting those targets.
- Assign remediation tasks to correct teams automatically.
In addition to auditing and reporting integration data quality, DCM can be used to ensure that integrated data is received properly and related to other data such as adding responsible persons, relationships to services, business applications and other records within the platform.
DCM then measures that these requirements are met and helps people to maintain data according to agreed data models.
Example data quality trend for Server and Workstation integrations and Business Application data manually maintained on the platform.
Get Started Quickly
In this article, I will show you a simple data model for user data and give examples of different use cases that could fail due to issues in foundation data. I will also tell you what you can do to prevent such issues.
Ownership is key to success. Let’s take a look at how you can establish ownership in your CMDB using the Consumer-Owner-Provider model.
When we interact with our clients and prospects, we are often asked about the right time to begin using Data Content Manager. We believe the correct answer is, without a doubt: Now.
Example from real life: A seemingly regular and insignificant server failure escalated into a Major Incident. The difference between believing and knowing your data is good was worth 2 Million Euros.
The internationally active management consultancy iTSM Group and Qualdatrix join forces on Data Content Manager. Both companies are ServiceNow partners helping ServiceNow customers to digitalize their core activities.
Read about evolution of the CSDM framework and see practical CSDM examples of Service Portfolio Data Models, based on our experiences.