Data Maintenance Automation

From CDQ
Capability/Data Maintenance Automation
Jump to navigation Jump to search
Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language. Data Maintenance Automation (category: Automation, sort rank: 240)
Short description Informal and short human-readable definition of a concept. Automated data entry by customizable company-specific business rules.
Description Informal and comprehensive human-readable definition of a concept. More and more data is to be maintained while having limited budgets or even budget cuts. Master data of business partners is often controlled by audits as this data may impact the balance sheet due to direct relationships with accounting. From the experience more than 80% of data change requests are correct and are not changed by additional reviews implemented in data maintenance workflows. The review of change requests is a major effort-driver while providing often no additional improvement of the data. CDQ provides users with the option to maintain automation rules that ensure that only records that apply to these rules are manually checked. Automation rules are identically maintained like community and custom data quality rules and executed via the same interfaces which provides users with an automation decision. Multiple predefined functions enable usage of CDQ services for automation decisions such as checking for trust scores of bank accounts and automating bank data updates when the score exceeds a certain threshold. Checking the existence of partners in the community data pool or trusted shared data sources allows for automated approval.
Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it. BETA
Use cases Not used in any use case
Apps No app provides this capability
APIs No API provides this capability

Features

Feature Short description Informal and short human-readable definition of a concept. Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it.
Custom Automation Rules Documentation and implementation of custom automation rules for data maintenance workflow automation BETA
Custom Rulebook Data quality- and automation rulebook customized for a client BETA
Detailed Automation Decision Result Comprehensive explanation and trace why a certain decision is proposed by the Automation Decision Engine BETA
Golden Record Generation Generate a consolidated, best-guess record by intelligently combining the input record and identified reference business partners (i.e. lookup matches) BETA
Augmented Record Configuration Configure the generation of an augmented record in terms of augmentation views (legal entity view, VAT registration view, operational locations view, business relationship/hierarchy view) and the reference data sources that are employed IDEA