SMDS-ADR-003
| Status | NOT STARTED / IN PROGRESS / COMPLETE |
|---|---|
| Impact | HIGH / MEDIUM / LOW |
| Driver | |
| Date |
Decisions
- Enhancing Data Integrity: Implementing Workflow Approval for Segment Data in SMDS CMD
Context
In the current SMDS CMD (Customer Master Data) system, customer information is updated and enriched via various channels such as the portal, internal automation processes, and external sources like BVD enrichment. While this system provides flexibility in updating customer core data, the handling of segment data—which involves critical customer information—lacks a formal approval mechanism.
Currently, both segment data and non-segment data can be updated in parallel without a robust validation process in place for segment information. This absence of controlled workflow and approval leads to potential risks where unverified or inconsistent data might be published, impacting downstream systems that rely on this data. Additionally, the system does not enforce checks to prevent updates to certain segment types without appropriate approvals, creating gaps in data quality and governance.
To address this, the proposed solution introduces a workflow approval lifecycle for specific segment types. This ensures that segment data is only published after being approved, enhancing the data integrity and compliance of the customer master data. After approval, the system will fetch and consolidate the latest stable segment data with the non-segment data, ensuring that only approved and synchronized datasets are published, thereby improving accuracy, consistency, and trust in the data.
Solution 1
In the proposed solution, the segmentation update workflow is separated from the CMD portal. The segment update workflow process is managed in a distinct application, allowing for the integration of approved changes into CMD almost instantaneously. The image below illustrates the data modifications and the workflow process.
In this method,
- All segment updates are halted from the CMD Portal, making it as read only.
- Customers will experience seamless regular updates (such as address, tax, or name changes), ensuring smooth business as usual (BAU) operations.
- The Segment Portal will consistently mirror the CMD Portal, as both platforms retrieve data from the same source.
- Segment automation as part of BVD enrichment will continue as usual.
Solution 2
The SMDS CMD Portal will offer a comprehensive functionality to update both customer core information and associated segment data. Currently, segment information is enriched through multiple channels, including:
- Portal: Manual entry and updates via the user interface.
- Internal Automation: Automated processes that enhance data accuracy and consistency.
- BVD Enrichment: Data enrichment via Bureau van Dijk, adding valuable business insights to segment data.
With the proposed solution, the SMDS CMD Portal will introduce a robust workflow approval lifecycle for certain segment types. This enhancement will ensure that segment data undergoes a formal approval process before being published, reinforcing data quality and governance. The segment data will only be published once it has successfully passed through this approval workflow, guaranteeing that only vetted and validated information is made available for downstream processes.
Process Flow
The data flow is divided into the following key steps:
- SMDS CMD Portal
- Source: Users submit data via the SMDS CMD Portal that includes segment and non-segment data
- Action: This payload is sent to the backend for further processing through the SMDS Ingest Service.
- SMDS Ingest Service
- Action: The SMDS Ingest Service receives the payload and splits it based on the presence of segmentation data.
- Categories:
- Non-Segment Data: Data that does not contain any segment-specific information.
- Segment Data: Data that contains segment-specific information, linked to the customer
- Data Split
- Non-Segment Data:
- Snapshot of data that does not have segment information.
- Flows through the Non-Segment Workflow.
- Segment Data:
- Snapshot of data containing segment-specific details.
- Flows through the Segment Workflow.
- Workflows and Workflow Indicators
Non-Segment Workflow
- Snapshot: Processes the current snapshot of non-segmented data.
- Approval Process: The workflow proceeds after any required approvals are obtained.
- Workflow Indicator: There is a workflow indicator in place to disable any updates to non-segment data until the necessary approvals are secured.
- Action: Once approval is secured, the system retrieves the latest stable non-segment data alongside the approved segment data. These datasets are then seamlessly concatenated to form a unified, validated record. This ensures that both non-segment and segment data are aligned, up-to-date, and ready for further processing or publication. The process enhances data consistency and reliability across the platform, ensuring that only approved and stable information is used in downstream workflows.
Segment Workflow
- Segment Information: Processes data that includes segment-related information.
- Approval Process: The workflow for segment data ensures all segment-related information is handled with care and proceeds only after approvals.
- Workflow Indicator: There is a workflow indicator in place to disable any updates to segment data until the required approvals are obtained.
- Action: Upon receiving approvals, the system retrieves the latest stable segment data, which is then concatenated with the stable non-segment data. This merging process ensures that both data types are synchronized, forming a comprehensive and up-to-date dataset. By consolidating approved segment and non-segment information, the platform ensures data integrity and readiness for subsequent workflows, providing a unified and validated source of truth for further processing or publication.
- Database and Publishing
- Both Non-Segment and Segment workflows deposit the approved and stable data into their respective databases.
- Once the stable data is saved, it is ready to be Published.